Add DeployMates/jev-seo (apps) - #151

One object appended to the projects array in data/projects.json, matching the shape in CONTRIBUTING.md. Category apps, since it is a product rather than an SDK, demo or benchmark.

{
  "name": "jev-seo (DeployMates)",
  "repo": "DeployMates/jev-seo",
  "site": "https://jev.mfrank.me/",
  "description": "Audits any business website for SEO and AI-answer-engine visibility: a deterministic crawler measures each page, Jev answers narrow typed questions over the extracted text, and the returned probabilities become ranked findings in a local dashboard.",
  "category": "apps",
  "language": "TypeScript",
  "stars": 0,
  "added": "2026-09-30"
}

Why it qualifies under "What gets listed"

• It actually calls Jev. server/src/jevClient.ts posts typed Choice / Score / Noul question sets to https://opencode.ai/zen/v1/systemone (model jev-1.13-free) and parses the documented response shape. The question registry is server/src/questions.ts.
• Public. Public repository, public npm package (jevseo), live site.
• One-sentence description, plain language, no numbers that need a source.

Things you should know before merging

• Name collision, and I used your disambiguation convention. This list already has jev-seo (AkashPriyadarshii/jev-seo, a Rust CLI/MCP suite, under Agent tooling) and jevseo (epergaboni/jevseo, under Demos & playgrounds). Both are unrelated projects. validate.mjs only dedupes on repo/url/site, so a duplicate name would have passed — but I followed the jev-mcp (jkudish) / typesafe-sdk-go (dwisiswant0) pattern and named it jev-seo (DeployMates). Happy to rename if you prefer something else.
• This repo is below your automated inclusion bar. discover --add requires 2+ stars, or 1 star with a site. DeployMates/jev-seo has 0 stars (created today), so the nightly job will never pick it up on its own — hence this manual PR. Flagging it plainly so you can close it if that bar is meant to apply to humans too.
• The repository is UNLICENSED, all rights reserved — package.json declares "license": "UNLICENSED" and there is no LICENSE file. Your inclusion rules do not ask for a license, so I have not treated this as disqualifying, but I did not want to imply otherwise.
• The site is a deployment of the project, not a TypeSafe product, and I am not claiming any relationship to TypeSafe AI.
• Affiliation and disclosure: I maintain this project, and its code is AI-assisted (it ships agent-facing AGENTS.md contracts).

What it does not claim

Jev carries no search index, volume data or backlink graph, so the tool publishes no search-volume numbers at all. It also makes no accuracy or ranking guarantee: its own README states the thresholds are a starting point that needs a few hundred labelled pages before they can be trusted. I deliberately kept all of that out of the description — if you would rather the entry state the no-search-volume limitation inline, say so and I will amend.

Verification

• npm run validate → data/projects.json: 1103 entries valid. (was 1102)
• Changed one file, 10 lines added: data/projects.json. README.md and site/index.html not touched, per your instruction that CI regenerates both after merge.

^{Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.}

Summary by CodeRabbit

• New Features
  • Added jev-seo (DeployMates) to the project catalog, including its website, repository, description, and project details.